Description

• Added a check to see if SQLCipher is available during run time when the DBEncryption feature is enabled, if not then the SDK will log an error message to the developer to ensure that the SQLCipher is linked well to the project.
• Refactored createDB method of RSDBPersistentManager to reduce its cognitive complexity by breaking down the method into multiple methods.
• Fixed the below issues in the of RSDBPersistentManager:
  • When an unencrypted database exists already in the app and the developer enables the encryption on the next run with a key. SDK will encrypt the unencrypted database and from then it will start saving events to the new encrypted database. But however, if SDK failed to encrypt the unencrypted database after opening it, SDK would keep writing events to the unencrypted database despite the developer enabling the encryption.
  • When an encrypted database exists already in the app and the developer disables the encryption on the next run with the valid key, then SDK will decrypt the encrypted database and from then it will start saving events to the new unencrypted database. But however, if SDK failed to decrypt the encrypted database after opening it, SDK would keep writing events to the encrypted database despite the developer disabling the encryption.
  • When an encrypted database exists already in the app and the developer disables the encryption on the next run with the valid key, then SDK will decrypt the encrypted database and from then it will start saving events to the new unencrypted database. But however, if SDK failed to open the encrypted database before trying to decrypt it for any reason, SDK would keep writing events to the encrypted database despite the developer disabling the encryption.